Skip to content

jetpack-mu-wpcom: add AI Launchpad cross-stream contract files#49562

Merged
Copons merged 1 commit into
trunkfrom
add/ai-launchpad-contracts
Jun 12, 2026
Merged

jetpack-mu-wpcom: add AI Launchpad cross-stream contract files#49562
Copons merged 1 commit into
trunkfrom
add/ai-launchpad-contracts

Conversation

@Copons

@Copons Copons commented Jun 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Fixes DOTOBRD-458

Proposed changes

  • Add src/features/ai-launchpad/contracts/agent-output-schema.json — the JSON Schema for the AI Launchpad's AI output shape (tasks, inferred, first_post_draft). This is the cross-stream contract: the upcoming tailor.ts validates model responses against it at runtime, the REST endpoint validates PUT /tailored bodies against it server-side, and Jest/PHPUnit suites assert against it.
  • Add src/features/ai-launchpad/contracts/eval-fixtures.json — six fixture cases (one per onboarding goal) used by prompt evaluation and manual smoke testing.
  • No runtime behavior change: nothing loads these files yet. Committing them first so that all upcoming AI Launchpad branches (and CI) can reference them by path.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  • Confirm both files parse as valid JSON: node -e "['agent-output-schema.json','eval-fixtures.json'].forEach(f => JSON.parse(require('fs').readFileSync('projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/contracts/' + f)))"
  • Confirm the schema is a valid JSON Schema draft-07 document (fields: $schema, $id, type, required, properties).
  • No code references these files yet, so there is nothing else to exercise — CI passing is sufficient.

@Copons Copons added the [Status] Needs Review This PR is ready for review. label Jun 11, 2026
@Copons Copons self-assigned this Jun 11, 2026
@github-actions

github-actions Bot commented Jun 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the add/ai-launchpad-contracts branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/ai-launchpad-contracts

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@jp-launch-control

jp-launch-control Bot commented Jun 11, 2026

Copy link
Copy Markdown

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report

@Copons Copons merged commit 99ae26b into trunk Jun 12, 2026
77 checks passed
@Copons Copons deleted the add/ai-launchpad-contracts branch June 12, 2026 09:32
@github-actions github-actions Bot removed the [Status] Needs Review This PR is ready for review. label Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@Copons Copons

Labels

[mu wpcom Feature] Ai Launchpad [Package] Jetpack mu wpcom WordPress.com Features

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Copons